Repository navigation
Conversation
Running the tool took two sources spelled out; in a repository, people and agents want to know what changed in their libraries since the last release. Without a command it now reads the directory's solution or project files, skips test and unpackable projects, and compares each project's Release build with its package's latest release. It does not build: a project without output is skipped with a warning. The github command, which cloned and built another commit, is dropped before its first release; the github| spec in diff still works and points at a git worktree recipe instead. Packages with no lib/ assemblies no longer crash the nuget provider. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Run without a command in a repository, assembly-differ now compares every library project's Release build with the latest release of its package. It skips test projects and projects that are not packable, and it does not build.
Prompt summary: Running assembly-differ without arguments, in a directory with a solution or project file, should report the changes by itself. That makes it easy for people and coding agents alike. It skips test projects and
IsPackable=falseprojects, each of which a flag includes, and a project flag picks projects. Building is left to the user, with a warning when there is no build output. The--buildorchestration of thegithubcommand is the tool doing too much, so it goes.Why
To see what a change does to a library's API, a person or an agent had to know the package id, the last version, the target framework and where the build output lives, then spell all of it out. An agent checking a change usually decompiled the assemblies itself instead.
What
projects, the default commandThe command reads the one
.slnxor.slnin the directory throughdotnet sln list, or else its project files. It asks MSBuild forIsPackable,IsTestProject,PackageId,AssemblyNameand the target frameworks. For the newest framework, it finds the ReleaseTargetPathand compares it with the latest stable release of the package on the NuGet.config feeds. Every project goes into one report. Each skipped project gets a line saying why and which flag includes it. A package with no release, or one that ships no matching assembly, such as a tool package, is reported and skipped.No building
The tool does not build. A project without Release output is skipped with a warning that says to run
dotnet build -c Release.--projectpicks project files explicitly, whatever kind they are. Two provider specs passed straight to the root, as before commands existed, are routed todiff, so those callers still work.githubcommand dropped,github|spec deprecatedThe
githubcommand cloned another commit and ran a build command the user had to spell out; it merged in #75 and was never released. Thegithub|...spec in the hiddendiffstill works and now warns on stderr. The README shows the replacement:git worktree add,dotnet build, thenassembly-differ files.A crash fixed
A package with no assemblies under
lib/, such as one that only ships an analyzer, crashed the NuGet provider with "Sequence contains no elements". It now reports that and compares nothing.Verify
🤖 Generated with Claude Code